Measurement reporting configuration for aiding the sorting of beam/cell level measurements

ABSTRACT

According to certain embodiments, a method performed by a wireless device ( 110 ) for measurement reporting includes sorting a plurality of measurements for a measurement report based on at least one measurement quantity. The method further includes reporting, to a network node ( 160 ), measurement information selected from the plurality of measurements sorted based on the at least one measurement quantity.

RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 16/370,097 filed on Mar. 29, 2019, which is a Continuation ofInternational Patent Application PCT/IB2018/059355, filed Nov. 27, 2018,which claims the benefit of U.S. Provisional Application No. 62/592,216,filed Nov. 29, 2017 and entitled “Measurement reporting configurationfor aiding the sorting of beam/cell level measurements,” the disclosuresof which are all hereby incorporated by reference.

BACKGROUND

It has been agreed in RAN2 that the beam level reporting is supported inNR.

Specifically, it has been agreed that:

-   -   Beam measurement (based on New Radio-Synchronization Signal        (NR-SS) and Channel State Information-Reference Signal (CSI_RS))        can be included in the measurement report and can be configured        by the network (i.e., network configures the user equipment (UE)        to report beam identifier only, beam measurement result and        identifier, or no beam reporting)    -   Measurement quantities can be configured by the network for beam        measurement reporting. RAN1 to confirm the measurement        quantities supported.    -   For selection of x synchronization signal (SS) blocks to be        included in the measurement report for each cell: x can be        configured separately from N (N used in cell quality        derivation).    -   Measurement quantity to be reported for beam measurements can be        the same as (cell) trigger quantity or both RSRP/RSRQ.    -   For measurement events based on NR-SS, in each cell the best SS        block is reported and up to x-1 next highest measured SS blocks        above the absolute threshold. Threshold is the same as that used        for cell quantity derivation.    -   For measurement events based on CSI-RS, in each cell the best        CSI-RS is reported and up to y-1 next highest measured CSI-RS        above the absolute threshold. Threshold is the same as that used        for cell quality derivation.    -   The beam level information (beam IDS and/or available        measurements results of primary cell (PCell)/primary secondary        cell (PSCell) and secondary cell (SCell) is included in the        measurement report if the network has configured the UE to do        so.        Based on these agreements, for an event triggered measurement        report, the UE shall report the beam level measurements of        PCell, PSCell, SCell, and cells in the triggeredCellsList.

Further, beam related measurement quantities to be reported for thecells in triggeredCellsList can be configured (independent of themeasurement quantities to be reported for the cells) as follows: Beamindex only, Beam index and beam RSRP, Beam index and beam RSRQ, or Beamindex and beam signal-to-interference-plus-noise ratio (SINR). In eachcell the best SS block/CSI-RS is always included in the measurementreport and up to x-1/y-1 next highest measured SS blocks/CSI-RS isincluded in the measurement report.

Additionally, there will be support for periodic measurement reportingin NR. Specifically, the following has been agreed in RAN2:

-   -   The current beam report agreements (network configures the UE to        report beam identifier only, beam measurement result and        identifier, or no beam reporting) applies to both        event-triggered reports and periodical reports.    -   A single periodical measurement configuration can be configured        to report SS based measured results or CSI-RS based measured        results (not both).    -   The UE is required to report all applicable cell up to        maxCellReport for periodical measurement, where the applicable        cells are defined as any neighbour cells detected on the        associated frequency except for the cell in black cell list.        Based on these agreements, the periodic measurement reports will        be based on only one RSType that is configured in the        corresponding reportConfig. Also, it has been agreed that the        beam level measurements are also included in the measurement        report.

In LTE, the triggerQuantity parameter, part of the reportingconfiguration (reportConfig), is not only used to indicate whichquantity shall be used for event triggered reporting such as, forexample, either RSRP, RSRQ or SINR. In addition, it may also be used forperiodical reporting. In addition to this parameter, reportConfig alsocontains a parameter called reportQuantity, used to indicate whichquantities shall be included in the measurement report. In other words,network may configure the UE to report more quantities than what isbeing used for triggering the event.

If the triggerQuantity is configured as RSRP and the reportQuantity isconfigured as sameAsTriggerQuantity, then the UE shall report the RSRPvalues. If the triggerQuantity is configured as RSRQ and thereportQuantity is configured as sameAsTriggerQuantity, then the UE shallreport the RSRQ values. Additionally, the reportQuantity can beconfigured as both, leading to reporting of both RSRP and RSRQ. InRelease-13, additional SINR based reporting were also introduced.

There currently exist certain challenge(s). Based on the aboveagreements for NR, the network may configure a UE to include beam levelmeasurement information (i.e., only beam indexes or beam indexes withmeasurement result(s)) for periodic measurement reporting as well asevent triggered measurement reports. It has already been agreed that theUE shall include the best beam for each cell and up to X-1 strongestbeams per cell above an absolute threshold in the measurement report,where X is configured in reportConfig and the threshold in themeasObject.

Additionally, the following has been argued to solve the problem and hasbeen submitted to RAN2 #100 in R2-1713427, which discusses correctionson RRM TP:

-   -   The current TP, the UE derives each cell quantity by the best N        beams for that quantity as below:        -   The UE shall:            -   1> for each cell measurement quantity to be derived                based on SS/PBCH block;            -   2> if nroSS-BlocksToAverage in the associated measObject                is not configured; or            -   2> if absThreshSS-BlocksConsolidation in the associated                measObject is not configured; or            -   2> if the highest beam measurement quantity value is                below absThreshSS-BlocksConsolidation:                -   3> derive each cell measurement quantity based on                    SS/PBCH block as the highest beam measurement                    quantity value, where each beam measurement quantity                    is described in TS 38.215 [FFS];            -   2> else:                -   3> derive each cell measurement quantity based on                    SS/PBCH block as the linear average of the power                    values of the highest beam measurement quantity                    values above absThreshSS-BlocksConsolidation where                    the total number of averaged beams shall not exceed                    nroSS-BlocksToAverage;    -   If multiple cell qualities (for example RSRQ and RSRQ) are        configured to report, the UE may have different sets of best N        beams for cell derivation considering the best N beams for RSRP        and RSRQ may be different. However, there has only one set of        beams in measurement report, the current TP says the UE should        include the best beam for each quantity, and other beams above        the threshold in decreasing order, but it is unclear on how to        sort these beams. If beams are sorted by different quantities        (for example RSRP or RSRQ), the results would be different.        -   For beam measurement information to be included in a            measurement report the UE shall:            -   1> set rsIndexResults to include up to                maxNroRsIndexesToReport beam indexes in order of                decreasing quantity as follows:                -   2> if the measurement information to be included is                    based on SS/PBCH block:                -    3> include within resultsSSBIndexes the index                    associated to the best beam for that SS/PBCH block                    quantity and the remaining beams whose quantity is                    above absThreshSS-BlocksConsolidation defined in the                    VarMeasConfig for the corresponding measObject;                -    3> if onlyReportBeamIds is not configured, include                    the SS/PBCH based measurement results associated to                    each beam index;    -   To clarify the beam raking criteria for beams report, one        possible change is to sort the beams by the quantity triggered        by the event, but it is still unclear on how to sort beams for        periodical MR. another options is to indicate the quantity for        beams sort explicitly by the network, in that case an additional        configuration is needed to indicate the quantity for beam sort        in MR.    -   Proposal 6: the network needs to indicate the measurement        quantity for beam sort in measurement configuration if multiple        quantities are configured to report.

Thus, as it can be seen, the R2-1713427 contribution mentioned a firstsolution where that ‘triggerQuantity’ could be used as the measurementquantity to be used for sorting the beam level measurements to bereported. As it has been mentioned in the prior art itself, the problemwith that solution is that the triggerQuantity is defined only for eventtriggered in the NR RRC specifications, hence, it is ambiguous how theUE shall sort the beams to be included in measurement reports.

Then, the Contribution suggests a second solution where an explicitparameter indicates the UE how to sort the beams, some kind of beamsorting reporting parameter. While that solution can solve the problem,that is not the most efficient.

The problems with the second solution are that an extra parameter wouldhave to be defined in the specification and explicitly signalled to theUE. Also, another problem is that it only covers the case of a singletrigger quantity i.e. report is triggered based on a single quantityRSRP, RSRQ or SINR. In NR, it has been at least proposed that thenetwork should potentially configure multiple trigger quantities suchas, for example, RSRP and RSRQ; RSRQ and SINR; RSRP and SINR; RSRP, RSRQand SINR. Also, it has been proposed that these could be based onmultiple RS types, e.g., SS/PBCH block and CSI-RS.

Yet another problem relates to the following agreements in NR, relatedto beam reporting associated to the serving cells. Specifically, in RAN2#99bis Prague, it has been agreed that beam level information (beam IDsand/or available measurement results) of the PCell/PSCell and SCell isincluded in the measurement report if the network has configured the UEto do so.

There is still an open question whether the UE always includes servingcells' beam information in measurement reports, although one of thealternatives might likely be supported:

-   -   UE shall include in measurement report all available beam        measurement information for serving cell(s);    -   UE shall include in measurement report the available beam        measurement information for serving cell(s) according to        reportConfig associated to the report;

In other words, in LTE, UE shall include RSRP and RSRQ in measurementreports for each configured serving cell. That has also been agreed forNR. Hence, as for each frequency there is a single serving cell, thereis no need to solve the sorting problem for serving cell measurementreporting. However, in NR, it has been agreed that the network mayconfigure the UE to include beam measurement results associated to i)serving cells (PCell and SCell(s)) and the ii) best neighbor(s) inserving frequencies as discussed above. Hence, the solution(s) describedin the prior contribution and agreements ignore that aspect of servingcell measurements, which is yet another limitation.

Yet another problem relates to the following agreements in NR, relatedto beam reporting associated to the best neighbor cell(s) in eachserving frequency. In RAN2 #99bis Prague, it has been agreed that thenetwork can configure the UE to report the best neighbour cells in theserving frequencies. The agreement from RAN2 #99bis meeting allows forthe cell level measurements of the best neighbour cell in servingfrequencies to be included. However, the RSType to be used to performthe neighbour cell measurements is still not agreed. Though one canconfigure a separate information element to control what type of RSTypeto be used for performing the neighbour cell measurements in the servingfrequencies, it would be sufficient to have the same RSType as the oneused for the serving cells' measurements. It has already been agreedthat the RSType for the serving cells' measurement is same as the oneconfigured in the reportConfigNR. There is a possibility that thefollowing may be agreed in NR.

-   -   UE shall use the same RSType(s) to measure best neighbour cell        in the serving frequencies as that of serving cells'        measurements in those frequencies.

Like the RSType to be used for measuring the neighbour cell measurementsin the serving frequencies, the quantities to be measured could alsofollow the same principles. It is beneficial to the network to have samequantity to be reported for the best neighbour cell and the serving cellin the serving frequencies so that the network can compare thesemeasurements and take the decisions accordingly. As the RSRP and RSRQmeasurements will always be reported for the serving cells, the sameshall be applicable to the best neighbouring cells in those servingfrequencies. The SINR reporting as mentioned in the previous section canbe dependent on the contents of the report quantity of the measID thattriggered the measurement report. Then, there is also a possibility thatthe following is also agreed in NR:

-   -   UE shall use the same measurement quantity for reporting cell        level measurements of best neighbour cell in the serving        frequencies as that of serving cells' measurements in those        frequencies.

The beam level information of the best neighbour cell in the servingfrequencies is not always needed. In those cases when it is needed, thenetwork can obtain the same by having specific events related to thesame (e.g., A6 event). However, configuring additional A6 events justfor the purpose of obtaining best neighbor cell beam level informationin serving frequencies could lead to increase in the number ofmeasurements as configured for the UE. In order to overcome thisdrawback, there could be a trade-off i.e. one could have the beam levelinformation of the best neighbor cell in serving frequencies reported tothe network only if the UE is configured with the beam level reportingis enabled in the reportConfig of the measID that triggered themeasurement report. The following may also be agreed for NR:

-   -   UE shall include the beam level measurements of the best        neighbour cell in the serving frequencies in the measurement        report only if the beam level reporting is enabled in the        reportConfig of the measID that triggered the measurement        report.

In order to further reduce the reporting overhead, the UE could reportonly those quantities that are configured in the beam level reportingrelated parameter in the reportConfig of the measID that triggered themeasurement report.

-   -   shall include only those beam level measurement quantities of        the best neighbour cell in the serving frequencies that are        configured in the beam level reporting of the reportConfig in        the measID that triggered the measurement report.

In summary, beam level measurement information associated to bestneighbor(s) in each serving frequency may also be configured by thenetwork to be included by the UE in measurement reports. Hence, as thatproblem also did not exist in LTE or was not addressed by priorproposals, it still remains unsolved.

SUMMARY

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. Particular embodimentspropose a method to configure the user equipment (UE) to identify thequantity to be chosen for sorting the beam level measurements.

According to certain embodiments, a method performed by a wirelessdevice for measurement reporting includes sorting a plurality ofmeasurements for a measurement report based on at least one measurementquantity. The method further includes reporting, to a network node,measurement information selected from the plurality of measurementssorted based on the at least one measurement quantity.

According to certain embodiments, a wireless device for measurementreporting includes processing circuitry configured to sort a pluralityof measurements for a measurement report based on at least onemeasurement quantity and report, to a network node, measurementinformation selected from the plurality of measurements based on the atleast one measurement quantity.

According to certain embodiments, a method performed by a network nodefor configuring a wireless device for measurement reporting includesconfiguring the wireless device event-based measurement reporting andreceiving, from the wireless device, a measurement report comprisingmeasurement information selected from a plurality of measurements basedon a sorting of the plurality of measurements in response to detectionof an event.

According to certain embodiments, a network node for configuring awireless device for measurement reporting includes processing circuitryconfigured to configure the wireless device for event-based measurementreporting and receive, from the wireless device, a measurement reportcomprising measurement information selected from a plurality ofmeasurements based on a sorting of the plurality of measurements inresponse to detection of an event.

Certain embodiments may provide one or more of the following technicaladvantage(s). For example, certain embodiments may provide astandardized behaviour from the UE for sorting of the beams whichenables the network to build clever self-optimized network (SON)functions.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and theirfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a measurement reporting procedure, according tocertain embodiments,

FIG. 2 illustrates an example network, according to certain embodiments;

FIG. 3 illustrates an example network node, according to certainembodiments;

FIG. 4 illustrates an example wireless device, according to certainembodiments;

FIG. 5 illustrates an example embodiment of a UE, according to certainembodiments;

FIG. 6 illustrates a virtualization environment in which functionsimplemented by some embodiments may be virtualized, according to certainembodiments;

FIG. 7 illustrates a telecommunication network connected via anintermediate network to a host computer, according to certainembodiments;

FIG. 8 illustrates a host computer communicating via a base station witha user equipment over a partially wireless connection, according tocertain embodiments;

FIG. 9 illustrates an example method implemented in a communicationsystem, according to certain embodiments;

FIG. 10 illustrates another example method implemented in acommunication system, according to certain embodiments;

FIG. 11 illustrates another example method implemented in acommunication system, according to certain embodiments;

FIG. 12 illustrates another example method implemented in acommunication system, according to certain embodiments;

FIG. 13 illustrates an example method in a wireless network, accordingto certain embodiments;

FIG. 14 illustrates a schematic block diagram of an apparatus in awireless network, according to certain embodiments;

FIG. 15 illustrates an example method by a wireless device formeasurement reporting, according to certain embodiments;

FIG. 16 illustrates a schematic block diagram of an apparatus in awireless network, according to certain embodiments;

FIG. 17 illustrates an example method by a network node for configuringa wireless device for measurement reporting, according to certainembodiments; and

FIG. 18 illustrates a schematic block diagram of an apparatus in awireless network, according to certain embodiments.

DETAILED DESCRIPTION

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

The following embodiments are applicable for cell and beam levelmeasurement reporting at least in i) periodic measurement reportingincluding beam measurement information, ii) event triggered measurementreporting including beam measurement information.

In the case of event triggered measurement reporting, certainembodiments may assume the following cases for the problem of sortingthe beam measurement information and cells based on these cases:

-   -   Single trigger quantity based on single RS type:        -   RSRP, RSRQ or SINR; Any of them based on SS/PBCH block;        -   RSRP, RSRQ or SINR; Any of them based on CSI-RS;    -   Single trigger quantity based on multiple RS types:        -   RSRP, RSRQ or SINR; There can be the same trigger quantity            measured with different RS types.            -   For example, event could be configured to be triggered                based on two RSRP values, one measured based on SS/PBCH                block and another based on CSI-RS.            -   For example, event could be configured to be triggered                based on two RSRQ values, one measured based on SS/PBCH                block and another based on CSI-RS.            -   For example, event could be configured to be triggered                based on two SINR values, one measured based on SS/PBCH                block and another based on CSI-RS.        -   RSRP, RSRQ or SINR; Any of them based on CSI-RS;    -   Multiple trigger quantities based on single RS type per event:        -   RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and            SINR; All based on SS/PBCH block.        -   RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and            SINR; All based on CSI-RS.    -   Multiple trigger quantities based on multiple RS types per        event:        -   RSRP based on SS/PBCH block and RSRQ based on CSI-RS;        -   RSRP based on CSI-RS and RSRQ based on SS/PBCH block;        -   RSRP based on SS/PBCH block and SINR based on CSI-RS;        -   RSRP based on CSI-RS and SINR based on SS/PBCH block;        -   RSRQ based on SS/PBCH block and SINR based on CSI-RS;        -   RSRQ based on CSI-RS and SINR based on SS/PBCH block;        -   RSRP, RSRQ and SINR, based on any combinations of RS types.            For example, RSRP and RSRQ based on SS/PBCH block while SINR            based on CSI-RS. In another example, RSRP and SINR based on            SS/PBCH block while RSRQ based on CSI-RS.

According to certain embodiments, the network may configure differentbeam and cell level measurement information. For example, the networkmay configure the UE to report the following measurement informationbased on SS/PBCH block(s):

-   -   Measurement results per SS/PBCH block, per cell and/or beam;    -   SS/PBCH block(s) indexes (i.e. per beam when SS/PBCH blocks are        beamformed and configured for measurements).

The network may configure the UE to report the following measurementinformation based on CSI-RS resources:

-   -   Measurement results per CSI-RS resource, per cell and/or per        beam.    -   CSI-RS resource measurement identifiers.

According to certain embodiments, a single parameter, which may becalled a triggerQuantity, is defined in reportConfig as a multi-purposeparameter and defined for multiple event types.

In a particular embodiment, for example, the single parameter calledtriggerQuantity may be defined in reportConfig for event triggeredreport type and periodical report type as a common parameter. Theparameter triggerQuantity may be defined in reportConfig can be encodedas followed triggerQuantity::=ENUMERATED {rsrp, rsrq, sinr}.

Below are some examples of how that common parameter could be coded inASN.1. For example, triggerQuantity can be valid for multiple reporttypes e.g. periodical or eventTriggered and coded outside reportType, asshown below:

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI Type_FFS!, ... }, triggerQuantity ENUMERATED {rsrp, rsrq,sinr} } EventTriggerConfig::= SEQUENCE { eventId CHOICE { eventA1SEQUENCE { a1-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN,hysteresis Hysteresis, timeToTrigger TimeToTrigger }, eventA2 SEQUENCE {a2-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger }, eventA3 SEQUENCE { a3-OffsetMeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL },eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity, reportOnLeaveBOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger,useWhiteCellList BOOLEAN OPTIONAL }, eventA5 SEQUENCE { a5-Threshold1MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, reportOnLeaveBOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger,useWhiteCellList BOOLEAN OPTIONAL }, eventA6 SEQUENCE { a6-OffsetMeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, },rsType ENUMERATED {ss, csi-rs}, reportInterval ReportInterval,reportAmount ENUMERATED {FFS!}, reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport), reportQuantityRsIndexesMeasReportQuantity OPTIONAL, maxNroRsIndexesToReport  INTEGER(1..maxNroIndexesToReport) OPTIONAL, onlyReportBeamIds BOOLEAN OPTIONALreportAddNeighMeas TYPE_FFS! } PeriodicalReportConfig ::= SEQUENCE {rsType ENUMERATED {ss, csi-rs}, reportInterval ReportInterval,reportAmount ENUMERATED {FFS!}, reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport), reportQuantityRsIndexesMeasReportQuantity OPTIONAL, maxNroRsIndexesToReport INTEGER(1..maxNroIndexesToReport) OPTIONAL, onlyReportBeamIds BOOLEAN OPTIONAL} MeasTriggerQuantity::= CHOICE { rsrp RSRPRange, rsrq RSRQRange, sinrSINRRange } MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!)OPTIONAL, rsrq INTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M -- TAG-REPORT-CONFIG-START -- ASN1STOP

According to other embodiments, the same multi-purpose parametertriggerQuantity can be encoded within each reportType that it is mean tobe used such as periodical or eventTriggered, as shown below:

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI TYPE_FFS!, ... } } EventTriggerConfig::= SEQUENCE { eventIdCHOICE { eventA1 SEQUENCE { a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, eventA4 SEQUENCE {a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA6 SEQUENCE { a6-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, }, rsType ENUMERATED{ss, csi-rs}, reportInterval ReportInterval, reportAmount ENUMERATED{FFS!}, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} reportQuantityCellMeasReportQuantity, maxReportCells INTEGER (1..maxCellReport),reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL reportAddNeighMeas TYPE_FFS! }PeriodicalReportConfig ::= SEQUENCE { rsType ENUMERATED {ss, csi-rs},reportInterval ReportInterval, reportAmount ENUMERATED {FFS!},triggerQuantity ENUMERATED {rsrp, rsrq, sinr} reportQuantityCellMeasReportQuantity, maxReportCells INTEGER (1..maxCellReport),reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER 1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL } MeasTriggerQuantity::= CHOICE {rsrp RSRPRange, rsrq RSRQRange, sinr SINRRange }MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!) OPTIONAL, rsrqINTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M

According to certain other embodiments, the parameter for eventtriggered report type within each event is encoded, as it might not beapplicable for other events to be introduced in the future, as shownbelow:

ReportConfigNR information element ReportConfigNR ::= SEQUENCE {reportType CHOICE { periodical PeriodicalReportConfig, eventTriggeredEventTriggerConfig, reportCGI TYPE_FFS!, ... } } EventTriggerConfig::=SEQUENCE { eventId CHOICE { eventA1 SEQUENCE{ a1-ThresholdMeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, triggerQuantity ENUMERATED {rsrp, rsrq,sinr} }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} }, eventA3SEQUENCE { a3-Offset MeasTriggerQuantityOffset, reportOnLeave BOOLEAN,hysteresis Hysteresis, timeToTrigger TimeToTrigger, useWhiteCellListBOOLEAN OPTIONAL, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} },eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity, reportOnLeaveBOOLEAN, hysteresis Hysteresis, timeToTrigger TimeToTrigger,useWhiteCellList BOOLEAN OPTIONAL, triggerQuantity ENUMERATED {rsrp,rsrq, sinr} }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} }, eventA6SEQUENCE { a6-Offset MeasTriggerQuantityOffset, reportOnLeave BOOLEAN,hysteresis Hysteresis, timeToTrigger TimeToTrigger, useWhiteCellListBOOLEAN OPTIONAL, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} }, },rsType ENUMERATED {ss, csi-rs}, reportInterval ReportInterval,reportAmount ENUMERATED {FFS!}, reportQuantityCell MeasReportQuantity,maxReportCells INTEGER (1..maxCellReport), reportQuantityRsIndexesMeasReportQuantity OPTIONAL, maxNroRsIndexesToReport INTEGER(1..maxNroIndexesToReport) OPTIONAL, onlyReportBeamIds BOOLEAN OPTIONALreportAddNeighMeas TYPE_FFS! } PeriodicalReportConfig ::= SEQUENCE {rsType ENUMERATED {ss, csi-rs}, reportInterval ReportInterval,reportAmount ENUMERATED {FFS!}, triggerQuantity ENUMERATED {rsrp, rsrq,sinr} reportQuantityCell MeasReportQuantity, maxReportCells INTEGER(1..maxCellReport), reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL } MeasTriggerQuantity::= CHOICE {rsrp RSRPRange, rsrq RSRQRange, sinr SINRRange }MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!) OPTIONAL, rsrqINTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M -- TAG-REPORT-CONFIG-START -- ASN1STOP

According to certain embodiments, UE actions may be taken depending onthe parameter value in reportConfig for a measurement identifier(measId), which can be: ‘rsrp’, ‘rsrq’ or ‘sinr’. As examples, the UEshall:

-   -   If event triggered report type is configured and if beam        reporting is configured for that event or,    -   If periodical report type is configured and if beam reporting is        configured for that report type:        -   UE shall sort neighbor cell measurement results to be            included in measurement reports based on the configured            value i.e. if network configures ‘rsrp’, both cell            measurement results and beam measurement information are            sorted based on RSRP measurements (cell RSRP values and L3            filtered beam RSRP values, either based on SS/PBCH block or            CSI-RS).    -   If periodical report type is configured and if beam reporting is        configured for that report type:        -   UE shall assume the configured parameter as the trigger            quantity for that configured event i.e. RSRP, RSRQ or SINR.    -   When the UE is to include for configured serving cell(s) beam        measurement information, there can be multiple beams per cell        and sorting is needed. Hence, the UE shall:        -   If the beams to be reported have measurements associated to            only one RS type, set the measResult to include the            quantity(ies) indicated in the reportQuantity within the            concerned reportConfig in order of decreasing            triggerQuantity, i.e. the best beam associated to the            triggerQuantity for the available RS type is included first;    -   When the UE is to include for configured best neighbor(s) in        each serving frequency, beam measurement information, there can        be multiple beams per best neighbor cell and sorting is needed.        Hence, the UE shall:        -   If the beams to be reported have measurements associated to            only one RS type, set the measResult to include the            quantity(ies) indicated in the reportQuantity within the            concerned reportConfig in order of decreasing            triggerQuantity, i.e. the best beam associated to the            triggerQuantity for the available RS type is included first;

According to certain embodiments, the parameter may be said to bemulti-purpose in the sense that it is also used to indicate the orderingto include beam measurement information associated to the servingcell(s) and best neighbor(s) in serving frequency(ies) in measurementreports, i.e., ordered by RSRP, RSRQ or SNIR.

In another embodiment, the existing parameter rsType in reportConfig,which can take values SS/PBCH block or CSI-RS, is also multi-purpose. Asdefined in the current 38.331DRAFT specifications, the parameter is onlyused for selecting which RS type should be used for neighbormeasurements associated to that report type. As proposed in thisembodiment, it shall be used, in addition, for additional UE actionsrelated to sorting beams associated to serving cells to include inmeasurement reports.

-   -   If event triggered report type is configured or,    -   If periodical report type is configured,        -   If the beams associated to configured serving cell(s) to be            reported have measurements associated to multiple RS            type(s), e.g. SS/PBCH block and CSI-RS, set the measResult            to include the quantity(ies) indicated in the reportQuantity            within the concerned reportConfig in order of decreasing            triggerQuantity associated to the same rsType in            reportConfig that triggered the report i.e. the best beam            associated to the triggerQuantity measured using the            configured rsType is included first; In other words, let us            assume that the UE has available beam measurement            information (e.g. both RSRP and RSRQ) associated to CSI-RS            and SS/PBCH blocks (SSB). Then, if triggerQuantity is rsrp,            sorting shall occur based on RSRP. However, there can be two            RSRP values, one based on SSB and another based on CSI-RS.            The one to be used as sorting criteria shall be SSB if            rsType in reportConfig is SSB. Else, the one to be used as            sorting criteria shall be CSI-RS if rsType in reportConfig            is CSI-RS;    -   When the UE is to include for configured best neighbor(s) in        each serving frequency, beam measurement information, the notion        of the “best” cell or cells may vary depending on the quantity        (best RSRP? Best RSRQ?best SINR?) and RS type (best according to        SSB? Best according to CSI-RS?). Hence, in the case the UE has        available multiple of these measurements and shall include the K        best cell(s) only the UE shall:        -   If the best cells in configured serving frequency(ies) to be            reported have measurements associated to multiple RS            type(s), e.g. SS/PBCH block and CSI-RS, set the measResult            to include the quantity(ies) indicated in the reportQuantity            within the concerned reportConfig in order of decreasing            triggerQuantity associated to the same rsType in            reportConfig that triggered the report i.e. the best cell            associated to the triggerQuantity measured using the            configured rsType is included first; In other words, let us            assume that the UE has available cell measurements (e.g.            both RSRP and RSRQ) associated to CSI-RS and SS/PBCH blocks            (SSB). Then, if triggerQuantity is rsrp, sorting shall occur            based on RSRP. However, there can be two RSRP values, one            based on SSB and another based on CSI-RS. The one to be used            as sorting criteria shall be SSB if rsType in reportConfig            is SSB. Else, the one to be used as sorting criteria shall            be CSI-RS if rsType in reportConfig is CSI-RS;        -   If the best beams of best cell(s) in configured serving            frequency(ies) to be reported have measurements associated            to multiple RS type(s), e.g. SS/PBCH block and CSI-RS, set            the measResult to include the quantity(ies) indicated in the            reportQuantity within the concerned reportConfig in order of            decreasing triggerQuantity associated to the same rsType in            reportConfig that triggered the report i.e. the best cell            associated to the triggerQuantity measured using the            configured rsType is included first; In other words, let us            assume that the UE has available cell measurements (e.g.            both RSRP and RSRQ) associated to CSI-RS and SS/PBCH blocks            (SSB). Then, if triggerQuantity is rsrp, sorting shall occur            based on RSRP. However, there can be two RSRP values, one            based on SSB and another based on CSI-RS. The one to be used            as sorting criteria shall be SSB if rsType in reportConfig            is SSB. Else, the one to be used as sorting criteria shall            be CSI-RS if rsType in reportConfig is CSI-RS;

If the beams to be reported have measurements associated to multiple RStype(s), e.g. SS/PBCH block and CSI-RS, set the measResult to includethe quantity(ies) indicated in the reportQuantity within the concernedreportConfig in order of decreasing triggerQuantity associated to thesame rsType in reportConfig i.e. the best beam associated to thetriggerQuantity measured using the configured rsType is included first.

FIG. 1 illustrates a measurement reporting procedure, according tocertain embodiments. With regard to the measurement reporting procedure,procedural text could be written for NR RRC specifications 38.331 asfollows:

-   -   The purpose of this procedure is to transfer measurement results        from the UE to the network. The UE shall initiate this procedure        only after successful security activation.    -   For the measId for which the measurement reporting procedure was        triggered, the UE shall set the measResults within the        MeasurementReport message as follows:        -   1> set the measId to the measurement identity that triggered            the measurement reporting;        -   1> set the measResultServingCell within            measResultServingFreqList to include the all available cell            and beam quantities of the PCell based on SS/PBCH block and            CSI-RS measurements;        -   1> set the measResultServingCell within            measResultServFreqList to include for each SCell that is            configured, if any, the servFreqId and all the available            cell and beam quantities of the concerned SCell based on            SS/PBCH block and CSI-RS measurements, if available            according to performance requirements in TS 38.133;        -   1> if the reportConfig associated with the measId that            triggered the measurement reporting includes            reportAddNeighMeas:            -   2> for each serving frequency for which measObjectId is                referenced in the measIdList, other than the frequency                corresponding with the measId that triggered the                measurement reporting:                -   3> set the measResultBestNeighCell within                    measResultServFreqList to include the physCellId and                    the quantities of the best non-serving cell on the                    concerned serving frequency;    -   [Details of the information to be reported concerning best        neighbouring cells in the serving frequencies e.g. which RS        type, which quantities, whether beam reporting is supported,        etc. are for future study. Additionally, whether the UE shall        include all available beam information of the PCell/SCells in a        measurement report or whether the UE shall only include the beam        information of PCell/PSCell that is indicated in the        reportConfig associated to that measId are for future study.]        -   1> if there is at least one applicable neighbouring cell to            report:            -   2> set the measResultNeighCells to include the best                neighbouring cells up to maxReportCells in accordance                with the following:                -   3> if the reportType is set to eventTriggered:                -    4> include the cells included in the                    cellsTriggeredList as defined within the                    VarMeasReportList for this measId;            -   3> else:                -   4> include the applicable cells for which the new                    measurement results became available since the last                    periodical reporting or since the measurement was                    initiated or reset;                -   4> if reportQuantityRsIndexes is configured, include                    beam measurement information as described in                    5.5.5.1;            -   3> for each cell that is included in the                measResultNeighCells, include the physCellId;            -   3> if the reportType is set to eventTriggered;                -   4> for each included cell, include the layer 3                    filtered measured results in accordance with the                    reportConfig for this measId, ordered as follows:                -    5> if the measObject associated with this measId                    concerns NR:                -     6> if rsType in the associated reportConfig is set                    to ss:                -      > set resultsSSBCell within the measResult to                    include the SS/PBCH block based quantity(ies)                    indicated in the reportQuantityCell within the                    concerned reportConfig, in order of decreasing                    quantity indicated in the triggerQuantity parameter,                    i.e. the best cell is included first;                -      > if reportQuantityRsIndexes is configured,                    include beam measurement information as described in                    5.5.5.1;                -     6> if                -     6> if rsType in the associated reportConfig is set                    to csi-rs:                -      7> set resultsCSI-RSCell within the measResult to                    include the CSI-RS based quantity(ies) indicated in                    the reportQuantityCell within the concerned                    reportConfig, in order of decreasing quantity                    indicated in the triggerQuantity parameter, i.e. the                    best cell is included first;                -       8> if reportQuantityRsIndexes is configured,                    include beam measurement information as described in                    5.5.5.1;        -   1> increment the numberOfReportsSent as defined within the            VarMeasReportList for this measId by 1;        -   1> stop the periodical reporting timer, if running;        -   1> if the numberOfReportsSent as defined within the            VarMeasReportList for this measId is less than the            reportAmount as defined within the corresponding            reportConfig for this measId:            -   2> start the periodical reporting timer with the value                of reportInterval as defined within the corresponding                reportConfig for this measId;        -   1> else:            -   2> if the reportType is set to periodical:                -   3> remove the entry within the VarMeasReportList for                    this measId;                -   3> remove this measId from the measIdList within                    VarMeasConfig;        -   1> submit the MeasurementReport message to lower layers for            transmission, upon which the procedure ends;

5.5.5.1 Reporting of Beam Measurement Information

-   -   For beam measurement information to be included in a measurement        report associated to neighbour the UE shall:        -   1> if the measurement information to be included is            associated to serving cell(s) and both SS/PBCH block and            CSI-RS measurements are available, consider the beam            ordering to be based on measurements performed on the rsType            configured in reportConfig;        -   1> if the measurement information to be included is            associated to best neighbour cell(s) in the serving            frequency(ies) and both SS/PBCH block and CSI-RS            measurements are available, consider the beam ordering to be            based on measurements performed on the rsType configured in            reportConfig;        -   1> set rsIndexResults to include up to            maxNroRsIndexesToReport beam indexes in order of decreasing            quantity indicated in the triggerQuantity parameter as            follows:            -   2> if the measurement information to be included is                based on SS/PBCH block:                -   3> include within resultsSSBIndexes the index                    associated to the best beam for that SS/PBCH block                    quantity and the remaining beams whose quantity is                    above absThreshSS-BlocksConsolidation defined in the                    VarMeasConfig for the corresponding measObject;                -   3> if onlyReportBeamIds is not configured, include                    the SS/PBCH based measurement results associated to                    each beam index;            -   2> if the beam measurement information to be included is                based on CSI-RS:                -   3> include within resultsCSI-RSIndexes the index                    associated to the best beam for that CSI-RS quantity                    and the remaining beams whose quantity is above                    absThreshCSI-RS-Consolidation defined in the                    VarMeasConfig for the corresponding measObject;                -   3> if onlyReportBeamIds is not configured, include                    the CSI-RS based measurement results associated to                    each beam index;

According to certain other embodiments, the single parameter calledtriggerQuantity may be defined in reportConfig for event triggeredreport type and periodical report type as a common parameter. Theparameter triggerQuantity is defined in reportConfig can be encoded asfollows:

triggerQuantity ::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN}.Hence, the previous set of embodiments are applicable if the networkconfigures a single trigger quantity i.e. if only one quantity isselected (i.e. set to TRUE) and all remaining are set to FALSE.

Below we show some examples of how that common parameter could be codedin ASN.1. For example, triggerQuantity can be valid for multiple reporttypes e.g. periodical or eventTriggered and coded outside reportType, asshown below:

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI TYPE_FFS!, ... }, triggerQuantity SEQUENCE { rsrp BOOLEAN,rsrq BOOLEAN, sinr BOOLEAN } } EventTriggerConfig::= SEQUENCE { eventIdCHOICE { eventA1 SEQUENCE{ a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, eventA4 SEQUENCE {a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA6 SEQUENCE { a6-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, }, rsType ENUMERATED{ss, csi-rs}, reportInterval ReportInterval, reportAmount ENUMERATED{FFS!}, reportQuantityCell MeasReportQuantity, maxReportCells INTEGER(1..maxCellReport), reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL reportAddNeighMeas TYPE_FFS! }PeriodicalReportConfig ::= SEQUENCE { rsType ENUMERATED {ss, csi-rs},reportInterval ReportInterval, reportAmount ENUMERATED {FFS!},reportQuantityCell MeasReportQuantity, maxReportCells INTEGER(1..maxCellReport), reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL } MeasTriggerQuantity::= CHOICE {rsrp RSRPRange, rsrq RSRQRange, sinr SINRRange }MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!) OPTIONAL, rsrqINTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M -- TAG-REPORT-CONFIG-START -- ASN1STOP

In another example, the same multi-purpose parameter triggerQuantity canbe encoded within each reportType that it is mean to be used such asperiodical or eventTriggered, as shown below:

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI TYPE_FFS!, ... } } EventTriggerConfig::= SEQUENCE { eventIdCHOICE { eventA1 SEQUENCE { a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger }, eventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, eventA4 SEQUENCE {a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL }, eventA6 SEQUENCE { a6-Offset MeasTriggerQuantityOffset,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL }, }, rsType ENUMERATED{ss, csi-rs}, reportInterval ReportInterval, reportAmount ENUMERATED{FFS!}, triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } -- Cell reporting configuration reportQuantityCellMeasReportQuantity, maxReportCells INTEGER (1..maxCellReport), -- RSindex reporting configuration reportQuantityRsIndexes MeasReportQuantityOPTIONAL, maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport)OPTIONAL, onlyReportBeamIds BOOLEAN OPTIONAL reportAddNeighMeasTYPE_FFS! } PeriodicalReportConfig ::= SEQUENCE { rsType ENUMERATED {ss,csi-rs}, reportInterval ReportInterval, reportAmount ENUMERATED {FFS!},triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN }reportQuantityCell MeasReportQuantity, maxReportCells INTEGER(1..maxCellReport), reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL, } MeasTriggerQuantity::= CHOICE {rsrp RSRPRange, rsrq RSRQRange, sinr SINRRange }MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!) OPTIONAL, rsrqINTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M -- TAG-REPORT-CONFIG-START -- ASN1STOP

In yet another example, the parameter for event triggered report typemay be encoded within each event, as it might not be applicable forother events to be introduced in the future, as shown below:

ReportConfigNR information element -- ASN1START --TAG-REPORT-CONFIG-START ReportConfigNR ::= SEQUENCE { reportType CHOICE{ periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig,reportCGI TYPE_FFS!, ... } } EventTriggerConfig::= SEQUENCE { eventIdCHOICE { eventA1 SEQUENCE { a1-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN,sinr BOOLEAN } }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeave BOOLEAN, hysteresis Hysteresis, timeToTriggerTimeToTrigger, triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN,sinr BOOLEAN } }, eventA3 SEQUENCE { a3-OffsetMeasTriggerQuantityOffset, reportOnLeave BOOLEAN, hysteresis Hysteresis,timeToTrigger TimeToTrigger, useWhiteCellList BOOLEAN OPTIONAL,triggerQuantity ENUMERATED {rsrp, rsrq, sinr} }, eventA4 SEQUENCE {a4-Threshold MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL, triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity,a5-Threshold2 MeasTriggerQuantity, reportOnLeave BOOLEAN, hysteresisHysteresis, timeToTrigger TimeToTrigger, useWhiteCellList BOOLEANOPTIONAL, triggerQuantity ENUMERATED {rsrp, rsrq, sinr} }, eventA6SEQUENCE { a6-Offset MeasTriggerQuantityOffset, reportOnLeave BOOLEAN,hysteresis Hysteresis, timeToTrigger TimeToTrigger, useWhiteCellListBOOLEAN OPTIONAL, triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN,sinr BOOLEAN } }, }, rsType ENUMERATED {ss, csi-rs}, reportIntervalReportInterval, reportAmount ENUMERATED {FFS!}, reportQuantityCellMeasReportQuantity, maxReportCells INTEGER (1..maxCellReport),reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL reportAddNeighMeas TYPE_FFS! }PeriodicalReportConfig ::= SEQUENCE { rsType ENUMERATED {ss, csi-rs},reportInterval ReportInterval, reportAmount ENUMERATED {FFS!},triggerQuantity SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN }reportQuantityCell MeasReportQuantity, maxReportCells INTEGER(1..maxCellReport), reportQuantityRsIndexes MeasReportQuantity OPTIONAL,maxNroRsIndexesToReport INTEGER (1..maxNroIndexesToReport) OPTIONAL,onlyReportBeamIds BOOLEAN OPTIONAL } MeasTriggerQuantity::= CHOICE {rsrp RSRPRange, rsrq RSRQRange, sinr SINRRange }MeasTriggerQuantityOffset::= CHOICE { rsrp INTEGER (FFS!) OPTIONAL, rsrqINTEGER (FFS!) OPTIONAL, sinr INTEGER (FFS!) OPTIONAL }MeasReportQuantity::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinrBOOLEAN } M -- TAG-REPORT-CONFIG-START -- ASN1STOP

In still other embodiments, the single parameter called triggerQuantitymay be defined in reportConfig for event triggered report type andperiodical report type as a common parameter. However, the parametertriggerQuantity defined in reportConfig can be encoded as follows:

triggerQuantity ::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN}.

And, in addition, the IE rsType is defined as a sequence, to indicatethat an event could be triggered based on multiple RS types.

rsType ::= SEQUENCE { ssb BOOLEAN, csi-rs BOOLEAN }·

According to certain other embodiments, the beam level quantity to beused for sorting the beam level measurements may be based on the sortingquantity selection method as specified in the measConfig and furtherbased on the triggerQuantity specified in the reportConfig. In thisembodiment, the network configures a mapping of triggerQuantity asspecified in the reportConfig and the quantity used for the sortingmethod to be used by the UE for beam selection. Some of these mapping isprovided in the table below (the following table will be provided in oneway or the other in the measConfig).

Measurement quantity to TriggerQuantity in the be used for the sortingof reportConfig beam level measurements RSRP RSRP RSRQ RSRQ SINR SINRRSRP and SINR RSRP RSRP and RSRQ RSRP RSRQ and SINR SINR RSRP and RSRQand SINR RSRP

In certain other embodiments, the beam level quantity to be used forsorting the beam level measurements is based on the sorting quantityselection method (mapping table) as specified in the measConfig andfurther based on the reportQuantityRsIndexes specified in thereportConfig. In this embodiment, the network configures a mapping ofreportQuantity as specified in the reportConfig and the quantity usedfor the sorting method to be used by the UE for beam selection. Some ofthese mapping is provided in the table below (the following table willbe provided in one way or the other in the measConfig).

reportQuantityRsIndexes in the Measurement quantity to reportConfigincludes following be used for the sorting of beam level reportingquantity. beam level measurements onlyReportBeamIds RSRP RSRP RSRP RSRQRSRQ SINR SINR RSRP and SINR RSRP RSRP and RSRQ RSRP RSRQ and SINR SINRRSRP and RSRQ and SINR RSRPIn other embodiments, where RSRQ and SINR are indicated for beam levelreporting, the measurement quantity to be used for the sorting of beamlevel measurements may be RSRQ.

In another particular embodiment, for the case of multiple triggerquantities (e.g. RSRP and RSRQ), there can be an explicit parameter(cellsSortingQuantity) so that the UE knows which quantity shall be usedfor sorting the cells to include in measurement reports.

In another particular embodiment, for the case of multiple triggerquantities (e.g. RSRP and RSRQ), there can be an explicit parameter(beamsSortingQuantity) so that the UE knows which quantity shall be usedfor sorting the cells to include in measurement reports.

In another particular embodiment, for the case of multiple triggerquantities (e.g. RSRP and RSRQ), there can be an explicit parameter(sortingQuantity) so that the UE knows which quantity shall be used forsorting cells and beams to include in measurement reports.

In another particular embodiment, for the case of multiple RS types astrigger quantities (e.g. SSB based RSRP and CSI-RS based RSRP), therecan be an explicit parameter (cellsSortingQuantity) so that the UE knowswhich RS type it shall be used for sorting the cells to include inmeasurement reports.

In another particular embodiment, for the case of multiple RS types astrigger quantities (e.g. SSB based RSRP and CSI-RS based RSRP), therecan be an explicit parameter (beamsSortingQuantity) so that the UE knowswhich quantity shall be used for sorting the beams per cell to includein measurement reports.

In another particular embodiment, multiple RS types as triggerquantities (e.g. SSB based RSRP and CSI-RS based RSRP), there can be anexplicit parameter (sortingQuantity) so that the UE knows which quantityshall be used for sorting cells and beams to include in measurementreports.

FIG. 2 illustrates a wireless network, in accordance with certainembodiments. Although the subject matter described herein may beimplemented in any appropriate type of system using any suitablecomponents, the embodiments disclosed herein are described in relationto a wireless network, such as the example wireless network illustratedin FIG. 2. For simplicity, the wireless network of FIG. 2 only depictsnetwork 106, network nodes 160 and 160 b, and WDs 110 and 110 b. Inpractice, a wireless network may further include any additional elementssuitable to support communication between wireless devices or between awireless device and another communication device, such as a landlinetelephone, a service provider, or any other network node or end device.Of the illustrated components, network node 160 and wireless device (WD)110 are depicted with additional detail. The wireless network mayprovide communication and other types of services to one or morewireless devices to facilitate the wireless devices' access to and/oruse of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 160 and WD 110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

FIG. 3 illustrates a network node, in accordance with some embodiments.As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 3, network node 160 includes processing circuitry 170, devicereadable medium 180, interface 190, auxiliary equipment 184, powersource 186, power circuitry 187, and antenna 162. Although network node160 illustrated in the example wireless network of FIG. 2 may representa device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods disclosed herein.Moreover, while the components of network node 160 are depicted assingle boxes located within a larger box, or nested within multipleboxes, in practice, a network node may comprise multiple differentphysical components that make up a single illustrated component (e.g.,device readable medium 180 may comprise multiple separate hard drives aswell as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node 160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium 180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna 162 may be shared by the RATs). Network node 160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node 160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node 160.

Processing circuitry 170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 170 may include processing informationobtained by processing circuitry 170 by, for example, converting theobtained information into other information, comparing the obtainedinformation or converted information to information stored in thenetwork node, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Processing circuitry 170 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 160 components, such as device readable medium 180, network node160 functionality. For example, processing circuitry 170 may executeinstructions stored in device readable medium 180 or in memory withinprocessing circuitry 170. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 170 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more ofradio frequency (RF) transceiver circuitry 172 and baseband processingcircuitry 174. In some embodiments, radio frequency (RF) transceivercircuitry 172 and baseband processing circuitry 174 may be on separatechips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceivercircuitry 172 and baseband processing circuitry 174 may be on the samechip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 170executing instructions stored on device readable medium 180 or memorywithin processing circuitry 170. In alternative embodiments, some or allof the functionality may be provided by processing circuitry 170 withoutexecuting instructions stored on a separate or discrete device readablemedium, such as in a hard-wired manner. In any of those embodiments,whether executing instructions stored on a device readable storagemedium or not, processing circuitry 170 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 170 alone or to other components ofnetwork node 160, but are enjoyed by network node 160 as a whole, and/orby end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 170. Device readable medium 180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 170 and, utilized by network node 160. Devicereadable medium 180 may be used to store any calculations made byprocessing circuitry 170 and/or any data received via interface 190. Insome embodiments, processing circuitry 170 and device readable medium180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication ofsignalling and/or data between network node 160, network 106, and/or WDs110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 tosend and receive data, for example to and from network 106 over a wiredconnection. Interface 190 also includes radio front end circuitry 192that may be coupled to, or in certain embodiments a part of, antenna162. Radio front end circuitry 192 comprises filters 198 and amplifiers196. Radio front end circuitry 192 may be connected to antenna 162 andprocessing circuitry 170. Radio front end circuitry may be configured tocondition signals communicated between antenna 162 and processingcircuitry 170. Radio front end circuitry 192 may receive digital datathat is to be sent out to other network nodes or WDs via a wirelessconnection. Radio front end circuitry 192 may convert the digital datainto a radio signal having the appropriate channel and bandwidthparameters using a combination of filters 198 and/or amplifiers 196. Theradio signal may then be transmitted via antenna 162. Similarly, whenreceiving data, antenna 162 may collect radio signals which are thenconverted into digital data by radio front end circuitry 192. Thedigital data may be passed to processing circuitry 170. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

In certain alternative embodiments, network node 160 may not includeseparate radio front end circuitry 192, instead, processing circuitry170 may comprise radio front end circuitry and may be connected toantenna 162 without separate radio front end circuitry 192. Similarly,in some embodiments, all or some of RF transceiver circuitry 172 may beconsidered a part of interface 190. In still other embodiments,interface 190 may include one or more ports or terminals 194, radiofront end circuitry 192, and RF transceiver circuitry 172, as part of aradio unit (not shown), and interface 190 may communicate with basebandprocessing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 162 may becoupled to radio front end circuitry 190 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 162 may comprise one or more omni-directional,sector or panel antennas operable to transmit/receive radio signalsbetween, for example, 2 GHz and 66 GHz. An omni-directional antenna maybe used to transmit/receive radio signals in any direction, a sectorantenna may be used to transmit/receive radio signals from deviceswithin a particular area, and a panel antenna may be a line of sightantenna used to transmit/receive radio signals in a relatively straightline. In some instances, the use of more than one antenna may bereferred to as MIMO. In certain embodiments, antenna 162 may be separatefrom network node 160 and may be connectable to network node 160 throughan interface or port. Antenna 162, interface 190, and/or processingcircuitry 170 may be configured to perform any receiving operationsand/or certain obtaining operations described herein as being performedby a network node. Any information, data and/or signals may be receivedfrom a wireless device, another network node and/or any other networkequipment. Similarly, antenna 162, interface 190, and/or processingcircuitry 170 may be configured to perform any transmitting operationsdescribed herein as being performed by a network node. Any information,data and/or signals may be transmitted to a wireless device, anothernetwork node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node 160with power for performing the functionality described herein. Powercircuitry 187 may receive power from power source 186. Power source 186and/or power circuitry 187 may be configured to provide power to thevarious components of network node 160 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 186 may either be included in,or external to, power circuitry 187 and/or network node 160. Forexample, network node 160 may be connectable to an external power source(e.g., an electricity outlet) via an input circuitry or interface suchas an electrical cable, whereby the external power source supplies powerto power circuitry 187. As a further example, power source 186 maycomprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 187. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 160 may include additionalcomponents beyond those shown in FIG. 3 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 160 may include user interface equipment to allow input ofinformation into network node 160 and to allow output of informationfrom network node 160. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node160.

FIG. 4 illustrates a wireless device (WD) 110, in accordance with someembodiments. As used herein, WD refers to a device capable, configured,arranged and/or operable to communicate wirelessly with network nodesand/or other wireless devices. Unless otherwise noted, the term WD maybe used interchangeably herein with user equipment (UE). Communicatingwirelessly may involve transmitting and/or receiving wireless signalsusing electromagnetic waves, radio waves, infrared waves, and/or othertypes of signals suitable for conveying information through air. In someembodiments, a WD may be configured to transmit and/or receiveinformation without direct human interaction. For instance, a WD may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the network. Examples of a WD include, but arenot limited to, a smart phone, a mobile phone, a cell phone, a voiceover IP (VoIP) phone, a wireless local loop phone, a desktop computer, apersonal digital assistant (PDA), a wireless cameras, a gaming consoleor device, a music storage device, a playback appliance, a wearableterminal device, a wireless endpoint, a mobile station, a tablet, alaptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment(LME), a smart device, a wireless customer-premise equipment (CPE). avehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114,processing circuitry 120, device readable medium 130, user interfaceequipment 132, auxiliary equipment 134, power source 136 and powercircuitry 137. WD 110 may include multiple sets of one or more of theillustrated components for different wireless technologies supported byWD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, orBluetooth wireless technologies, just to mention a few. These wirelesstechnologies may be integrated into the same or different chips or setof chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 114. In certain alternative embodiments, antenna 111 may beseparate from WD 110 and be connectable to WD 110 through an interfaceor port. Antenna 111, interface 114, and/or processing circuitry 120 maybe configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 111 may beconsidered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112and antenna 111. Radio front end circuitry 112 comprise one or morefilters 118 and amplifiers 116. Radio front end circuitry 114 isconnected to antenna 111 and processing circuitry 120, and is configuredto condition signals communicated between antenna 111 and processingcircuitry 120. Radio front end circuitry 112 may be coupled to or a partof antenna 111. In some embodiments, WD 110 may not include separateradio front end circuitry 112; rather, processing circuitry 120 maycomprise radio front end circuitry and may be connected to antenna 111.Similarly, in some embodiments, some or all of RF transceiver circuitry122 may be considered a part of interface 114. Radio front end circuitry112 may receive digital data that is to be sent out to other networknodes or WDs via a wireless connection. Radio front end circuitry 112may convert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 118and/or amplifiers 116. The radio signal may then be transmitted viaantenna 111. Similarly, when receiving data, antenna 111 may collectradio signals which are then converted into digital data by radio frontend circuitry 112. The digital data may be passed to processingcircuitry 120. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 110components, such as device readable medium 130, WD 110 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry120 may execute instructions stored in device readable medium 130 or inmemory within processing circuitry 120 to provide the functionalitydisclosed herein.

As illustrated, processing circuitry 120 includes one or more of RFtransceiver circuitry 122, baseband processing circuitry 124, andapplication processing circuitry 126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry120 of WD 110 may comprise a SOC. In some embodiments, RF transceivercircuitry 122, baseband processing circuitry 124, and applicationprocessing circuitry 126 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry124 and application processing circuitry 126 may be combined into onechip or set of chips, and RF transceiver circuitry 122 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 122 and baseband processing circuitry124 may be on the same chip or set of chips, and application processingcircuitry 126 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 122,baseband processing circuitry 124, and application processing circuitry126 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 122 may be a part of interface114. RF transceiver circuitry 122 may condition RF signals forprocessing circuitry 120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry 120 executing instructions stored on device readable medium130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 120 can be configured to perform the describedfunctionality. The benefits provided by such functionality are notlimited to processing circuitry 120 alone or to other components of WD110, but are enjoyed by WD 110 as a whole, and/or by end users and thewireless network generally.

Processing circuitry 120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 120, may include processinginformation obtained by processing circuitry 120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 130 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 120. Device readable medium 130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 120. In someembodiments, processing circuitry 120 and device readable medium 130 maybe considered to be integrated.

User interface equipment 132 may provide components that allow for ahuman user to interact with WD 110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment132 may be operable to produce output to the user and to allow the userto provide input to WD 110. The type of interaction may vary dependingon the type of user interface equipment 132 installed in WD 110. Forexample, if WD 110 is a smart phone, the interaction may be via a touchscreen; if WD 110 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 132 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 132 is configured to allow input of information into WD 110,and is connected to processing circuitry 120 to allow processingcircuitry 120 to process the input information. User interface equipment132 may include, for example, a microphone, a proximity or other sensor,keys/buttons, a touch display, one or more cameras, a USB port, or otherinput circuitry. User interface equipment 132 is also configured toallow output of information from WD 110, and to allow processingcircuitry 120 to output information from WD 110. User interfaceequipment 132 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits, ofuser interface equipment 132, WD 110 may communicate with end usersand/or the wireless network, and allow them to benefit from thefunctionality described herein.

Auxiliary equipment 134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 110 may further comprise power circuitry 137for delivering power from power source 136 to the various parts of WD110 which need power from power source 136 to carry out anyfunctionality described or indicated herein. Power circuitry 137 may incertain embodiments comprise power management circuitry. Power circuitry137 may additionally or alternatively be operable to receive power froman external power source; in which case WD 110 may be connectable to theexternal power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 137 may also in certain embodiments be operable to deliverpower from an external power source to power source 136. This may be,for example, for the charging of power source 136. Power circuitry 137may perform any formatting, converting, or other modification to thepower from power source 136 to make the power suitable for therespective components of WD 110 to which power is supplied.

FIG. 5 illustrates one embodiment of a UE 200, in accordance withvarious aspects described herein. As used herein, a user equipment or UEmay not necessarily have a user in the sense of a human user who ownsand/or operates the relevant device. Instead, a UE may represent adevice that is intended for sale to, or operation by, a human user butwhich may not, or which may not initially, be associated with a specifichuman user (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 200 may be any UE identified bythe 3^(rd) Generation Partnership Project (3GPP), including a NB-IoT UE,a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.UE 200, as illustrated in FIG. 5, is one example of a WD configured forcommunication in accordance with one or more communication standardspromulgated by the 3^(rd) Generation Partnership Project (3GPP), such as3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, theterm WD and UE may be used interchangeable. Accordingly, although FIG. 5is a UE, the components discussed herein are equally applicable to a WD,and vice-versa.

In FIG. 5, UE 200 includes processing circuitry 201 that is operativelycoupled to input/output interface 205, radio frequency (RF) interface209, network connection interface 211, memory 215 including randomaccess memory (RAM) 217, read-only memory (ROM) 219, and storage medium221 or the like, communication subsystem 231, power source 233, and/orany other component, or any combination thereof. Storage medium 221includes operating system 223, application program 225, and data 227. Inother embodiments, storage medium 221 may include other similar types ofinformation. Certain UEs may utilize all of the components shown in FIG.5, or only a subset of the components. The level of integration betweenthe components may vary from one UE to another UE. Further, certain UEsmay contain multiple instances of a component, such as multipleprocessors, memories, transceivers, transmitters, receivers, etc.

In FIG. 5, processing circuitry 201 may be configured to processcomputer instructions and data. Processing circuitry 201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 201 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configuredto provide a communication interface to an input device, output device,or input and output device. UE 200 may be configured to use an outputdevice via input/output interface 205. An output device may use the sametype of interface port as an input device. For example, a USB port maybe used to provide input to and output from UE 200. The output devicemay be a speaker, a sound card, a video card, a display, a monitor, aprinter, an actuator, an emitter, a smartcard, another output device, orany combination thereof. UE 200 may be configured to use an input devicevia input/output interface 205 to allow a user to capture informationinto UE 200. The input device may include a touch-sensitive orpresence-sensitive display, a camera (e.g., a digital camera, a digitalvideo camera, a web camera, etc.), a microphone, a sensor, a mouse, atrackball, a directional pad, a trackpad, a scroll wheel, a smartcard,and the like. The presence-sensitive display may include a capacitive orresistive touch sensor to sense input from a user. A sensor may be, forinstance, an accelerometer, a gyroscope, a tilt sensor, a force sensor,a magnetometer, an optical sensor, a proximity sensor, another likesensor, or any combination thereof. For example, the input device may bean accelerometer, a magnetometer, a digital camera, a microphone, and anoptical sensor.

In FIG. 5, RF interface 209 may be configured to provide a communicationinterface to RF components such as a transmitter, a receiver, and anantenna. Network connection interface 211 may be configured to provide acommunication interface to network 243 a. Network 243 a may encompasswired and/or wireless networks such as a local-area network (LAN), awide-area network (WAN), a computer network, a wireless network, atelecommunications network, another like network or any combinationthereof. For example, network 243 a may comprise a Wi-Fi network.Network connection interface 211 may be configured to include a receiverand a transmitter interface used to communicate with one or more otherdevices over a communication network according to one or morecommunication protocols, such as Ethernet, TCP/IP, SONET, ATM, or thelike. Network connection interface 211 may implement receiver andtransmitter functionality appropriate to the communication network links(e.g., optical, electrical, and the like). The transmitter and receiverfunctions may share circuit components, software or firmware, oralternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processingcircuitry 201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 219 maybe configured to provide computer instructions or data to processingcircuitry 201. For example, ROM 219 may be configured to store invariantlow-level system code or data for basic system functions such as basicinput and output (I/O), startup, or reception of keystrokes from akeyboard that are stored in a non-volatile memory. Storage medium 221may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 221 may be configured toinclude operating system 223, application program 225 such as a webbrowser application, a widget or gadget engine or another application,and data file 227. Storage medium 221 may store, for use by UE 200, anyof a variety of various operating systems or combinations of operatingsystems.

Storage medium 221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 221 may allow UE 200 to access computer-executable instructions,application programs or the like, stored on transitory or non-transitorymemory media, to off-load data, or to upload data. An article ofmanufacture, such as one utilizing a communication system may betangibly embodied in storage medium 221, which may comprise a devicereadable medium.

In FIG. 5, processing circuitry 201 may be configured to communicatewith network 243 b using communication subsystem 231. Network 243 a andnetwork 243 b may be the same network or networks or different networkor networks. Communication subsystem 231 may be configured to includeone or more transceivers used to communicate with network 243 b. Forexample, communication subsystem 231 may be configured to include one ormore transceivers used to communicate with one or more remotetransceivers of another device capable of wireless communication such asanother WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.4,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 233 and/or receiver 235 to implement transmitter orreceiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 233 andreceiver 235 of each transceiver may share circuit components, softwareor firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 200 or partitioned acrossmultiple components of UE 200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem231 may be configured to include any of the components described herein.Further, processing circuitry 201 may be configured to communicate withany of such components over bus 202. In another example, any of suchcomponents may be represented by program instructions stored in memorythat when executed by processing circuitry 201 perform the correspondingfunctions described herein. In another example, the functionality of anyof such components may be partitioned between processing circuitry 201and communication subsystem 231. In another example, thenon-computationally intensive functions of any of such components may beimplemented in software or firmware and the computationally intensivefunctions may be implemented in hardware.

FIG. 6 is a schematic block diagram illustrating a virtualizationenvironment 300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 300 hosted byone or more of hardware nodes 330. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 320 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 320 are run invirtualization environment 300 which provides hardware 330 comprisingprocessing circuitry 360 and memory 390. Memory 390 containsinstructions 395 executable by processing circuitry 360 wherebyapplication 320 is operative to provide one or more of the features,benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose orspecial-purpose network hardware devices 330 comprising a set of one ormore processors or processing circuitry 360, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 390-1 which may benon-persistent memory for temporarily storing instructions 395 orsoftware executed by processing circuitry 360. Each hardware device maycomprise one or more network interface controllers (NICs) 370, alsoknown as network interface cards, which include physical networkinterface 380. Each hardware device may also include non-transitory,persistent, machine-readable storage media 390-2 having stored thereinsoftware 395 and/or instructions executable by processing circuitry 360.Software 395 may include any type of software including software forinstantiating one or more virtualization layers 350 (also referred to ashypervisors), software to execute virtual machines 340 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 350 or hypervisor. Differentembodiments of the instance of virtual appliance 320 may be implementedon one or more of virtual machines 340, and the implementations may bemade in different ways.

During operation, processing circuitry 360 executes software 395 toinstantiate the hypervisor or virtualization layer 350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 350 may present a virtual operating platform thatappears like networking hardware to virtual machine 340.

As shown in FIG. 6, hardware 330 may be a standalone network node withgeneric or specific components. Hardware 330 may comprise antenna 3225and may implement some functions via virtualization. Alternatively,hardware 330 may be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 3100, which, among others, oversees lifecyclemanagement of applications 320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 340, and that part of hardware 530 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 340 on top of hardware networking infrastructure330 and corresponds to application 320 in FIG. 6.

In some embodiments, one or more radio units 3200 that each include oneor more transmitters 3220 and one or more receivers 3210 may be coupledto one or more antennas 3225. Radio units 3200 may communicate directlywith hardware nodes 330 via one or more appropriate network interfacesand may be used in combination with the virtual components to provide avirtual node with radio capabilities, such as a radio access node or abase station.

In some embodiments, some signalling can be effected with the use ofcontrol system 3230 which may alternatively be used for communicationbetween the hardware nodes 330 and radio units 3200.

FIG. 7 illustrates a telecommunication network connected via anintermediate network to a host computer in accordance with someembodiments. With reference to FIG. 7, in accordance with an embodiment,a communication system includes telecommunication network 410, such as a3GPP-type cellular network, which comprises access network 411, such asa radio access network, and core network 414. Access network 411comprises a plurality of base stations 412 a, 412 b, 412 c, such as NBs,eNBs, gNBs or other types of wireless access points, each defining acorresponding coverage area 413 a, 413 b, 413 c. Each base station 412a, 412 b, 412 c is connectable to core network 414 over a wired orwireless connection 415. A first UE 491 located in coverage area 413 cis configured to wirelessly connect to, or be paged by, thecorresponding base station 412 c. A second UE 492 in coverage area 413 ais wirelessly connectable to the corresponding base station 412 a. Whilea plurality of UEs 491, 492 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430,which may be embodied in the hardware and/or software of a standaloneserver, a cloud-implemented server, a distributed server or asprocessing resources in a server farm. Host computer 430 may be underthe ownership or control of a service provider, or may be operated bythe service provider or on behalf of the service provider. Connections421 and 422 between telecommunication network 410 and host computer 430may extend directly from core network 414 to host computer 430 or may govia an optional intermediate network 420. Intermediate network 420 maybe one of, or a combination of more than one of, a public, private orhosted network; intermediate network 420, if any, may be a backbonenetwork or the Internet; in particular, intermediate network 420 maycomprise two or more sub-networks (not shown).

The communication system of FIG. 7 as a whole enables connectivitybetween the connected UEs 491, 492 and host computer 430. Theconnectivity may be described as an over-the-top (OTT) connection 450.Host computer 430 and the connected UEs 491, 492 are configured tocommunicate data and/or signaling via OTT connection 450, using accessnetwork 411, core network 414, any intermediate network 420 and possiblefurther infrastructure (not shown) as intermediaries. OTT connection 450may be transparent in the sense that the participating communicationdevices through which OTT connection 450 passes are unaware of routingof uplink and downlink communications. For example, base station 412 maynot or need not be informed about the past routing of an incomingdownlink communication with data originating from host computer 430 tobe forwarded (e.g., handed over) to a connected UE 491. Similarly, basestation 412 need not be aware of the future routing of an outgoinguplink communication originating from the UE 491 towards the hostcomputer 430.

FIG. 8 illustrates a host computer communicating via a base station witha user equipment over a partially wireless connection, in accordancewith some embodiments. Example implementations, in accordance with anembodiment, of the UE, base station and host computer discussed in thepreceding paragraphs will now be described with reference to FIG. 8. Incommunication system 500, host computer 510 comprises hardware 515including communication interface 516 configured to set up and maintaina wired or wireless connection with an interface of a differentcommunication device of communication system 500. Host computer 510further comprises processing circuitry 518, which may have storageand/or processing capabilities. In particular, processing circuitry 518may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 510further comprises software 511, which is stored in or accessible by hostcomputer 510 and executable by processing circuitry 518. Software 511includes host application 512. Host application 512 may be operable toprovide a service to a remote user, such as UE 530 connecting via OTTconnection 550 terminating at UE 530 and host computer 510. In providingthe service to the remote user, host application 512 may provide userdata which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in atelecommunication system and comprising hardware 525 enabling it tocommunicate with host computer 510 and with UE 530. Hardware 525 mayinclude communication interface 526 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 500, as well as radiointerface 527 for setting up and maintaining at least wirelessconnection 570 with UE 530 located in a coverage area (not shown in FIG.8) served by base station 520. Communication interface 526 may beconfigured to facilitate connection 560 to host computer 510. Connection560 may be direct or it may pass through a core network (not shown inFIG. 8) of the telecommunication system and/or through one or moreintermediate networks outside the telecommunication system. In theembodiment shown, hardware 525 of base station 520 further includesprocessing circuitry 528, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 520 further has software 521 storedinternally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to.Its hardware 535 may include radio interface 537 configured to set upand maintain wireless connection 570 with a base station serving acoverage area in which UE 530 is currently located. Hardware 535 of UE530 further includes processing circuitry 538, which may comprise one ormore programmable processors, application-specific integrated circuits,field programmable gate arrays or combinations of these (not shown)adapted to execute instructions. UE 530 further comprises software 531,which is stored in or accessible by UE 530 and executable by processingcircuitry 538. Software 531 includes client application 532. Clientapplication 532 may be operable to provide a service to a human ornon-human user via UE 530, with the support of host computer 510. Inhost computer 510, an executing host application 512 may communicatewith the executing client application 532 via OTT connection 550terminating at UE 530 and host computer 510. In providing the service tothe user, client application 532 may receive request data from hostapplication 512 and provide user data in response to the request data.OTT connection 550 may transfer both the request data and the user data.Client application 532 may interact with the user to generate the userdata that it provides.

It is noted that host computer 510, base station 520 and UE 530illustrated in FIG. 8 may be similar or identical to host computer 430,one of base stations 412 a, 412 b, 412 c and one of UEs 491, 492 of FIG.7, respectively. This is to say, the inner workings of these entitiesmay be as shown in FIG. 8 and independently, the surrounding networktopology may be that of FIG. 7.

In FIG. 8, OTT connection 550 has been drawn abstractly to illustratethe communication between host computer 510 and UE 530 via base station520, without explicit reference to any intermediary devices and theprecise routing of messages via these devices. Network infrastructuremay determine the routing, which it may be configured to hide from UE530 or from the service provider operating host computer 510, or both.While OTT connection 550 is active, the network infrastructure mayfurther take decisions by which it dynamically changes the routing(e.g., on the basis of load balancing consideration or reconfigurationof the network).

Wireless connection 570 between UE 530 and base station 520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 530 using OTT connection 550,in which wireless connection 570 forms the last segment. More precisely,the teachings of these embodiments may improve the beam sorting behaviorof the UE in order to improve the ability to build self-optimizednetwork functionality.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 550 between host computer510 and UE 530, in response to variations in the measurement results.The measurement procedure and/or the network functionality forreconfiguring OTT connection 550 may be implemented in software 511 andhardware 515 of host computer 510 or in software 531 and hardware 535 ofUE 530, or both. In embodiments, sensors (not shown) may be deployed inor in association with communication devices through which OTTconnection 550 passes; the sensors may participate in the measurementprocedure by supplying values of the monitored quantities exemplifiedabove, or supplying values of other physical quantities from whichsoftware 511, 531 may compute or estimate the monitored quantities. Thereconfiguring of OTT connection 550 may include message format,retransmission settings, preferred routing etc.; the reconfiguring neednot affect base station 520, and it may be unknown or imperceptible tobase station 520. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating host computer 510's measurementsof throughput, propagation times, latency and the like. The measurementsmay be implemented in that software 511 and 531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 550 while it monitors propagation times, errors etc.

FIG. 9 is a flowchart illustrating a method implemented in acommunication system, in accordance with certain embodiments. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 5 and 6. Forsimplicity of the present disclosure, only drawing references to FIG. 9will be included in this section. In step 610, the host computerprovides user data. In substep 611 (which may be optional) of step 610,the host computer provides the user data by executing a hostapplication. In step 620, the host computer initiates a transmissioncarrying the user data to the UE. In step 630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 10 is a flowchart illustrating a method implemented in acommunication system, in accordance with certain embodiments. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 5 and 6. Forsimplicity of the present disclosure, only drawing references to FIG. 10will be included in this section. In step 710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with certain embodiments. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 5 and 6. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section. In step 810 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 820, the UE provides user data. In substep 821(which may be optional) of step 820, the UE provides the user data byexecuting a client application. In substep 811 (which may be optional)of step 810, the UE executes a client application which provides theuser data in reaction to the received input data provided by the hostcomputer. In providing the user data, the executed client applicationmay further consider user input received from the user. Regardless ofthe specific manner in which the user data was provided, the UEinitiates, in substep 830 (which may be optional), transmission of theuser data to the host computer. In step 840 of the method, the hostcomputer receives the user data transmitted from the UE, in accordancewith the teachings of the embodiments described throughout thisdisclosure.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with certain embodiments. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIGS. 5 and 6. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In step 910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step 930(which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

FIG. 13 depicts a method in a wireless network, in accordance withcertain embodiments. The method begins at step 1002 with determiningwhether event triggered, periodical, and/or beam reporting isconfigured. The method continues to step 1004 with sorting neighbourcell measurement results for a measurement report based on thedeterminations. The method continues to step 1006 with reporting to anetwork node a measurement report based on the determinations andsorting.

FIG. 14 illustrates a schematic block diagram of an apparatus 1100 in awireless network (for example, the wireless network shown in FIG. 2), inaccording to certain embodiments. The apparatus may be implemented in awireless device or network node (e.g., wireless device 110 or networknode 160 shown in FIG. 2). Apparatus 1100 is operable to carry out theexample method described with reference to FIG. 13 and possibly anyother processes or methods disclosed herein. It is also to be understoodthat the method of FIG. 13 is not necessarily carried out solely byapparatus 1100. At least some operations of the method can be performedby one or more other entities.

Virtual Apparatus 1100 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to causedetermining unit 1110, sorting unit 1120, and reporting unit 1130, anyother suitable units of apparatus 1100 to perform correspondingfunctions according one or more embodiments of the present disclosure,such as the functionality described in FIG. 14.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

FIG. 15 depicts a method by a wireless device 110 for measurementreporting, according to certain embodiments. The method begins at step1210 when wireless device 110 sorts a plurality of measurements for ameasurement report based on at least one measurement quantity.

In a particular embodiment, the measurement quantity is a reportquantity configured by the network. In another embodiment, themeasurement quantity is a trigger quantity out of a set of multipletrigger quantities configured by the network.

In a particular embodiment, the plurality of measurements comprises beamlevel measurements. Additionally or alternatively, the plurality ofmeasurements comprise cell level measurements.

In a particular embodiment, the plurality of measurements are for aserving cell of the wireless device. Additionally or alternatively, theplurality of measurements are for a neighbouring cell of the wirelessdevice.

At step 1220, wireless device 110 reports to a network node 160 themeasurement report comprising measurement information selected from theplurality of measurements based on the sorting of the plurality ofmeasurements based on the at least one measurement quantity.

In a particular embodiment, the measurement information includes atleast one of the plurality of measurements. Additionally oralternatively, the measurement information may include beam indexes.

In a particular embodiment, the measurement report includes beam levelinformation of a primary cell (PCell) and a secondary cell (SCell).

In a particular embodiment, the wireless device 110 detects fulfillmentof a measurement reporting criteria and sorts the plurality ofmeasurements for the measurement report in response to detecting thefulfillment of the measurement reporting criteria.

In a particular embodiment, wireless device 110 is configured forperiodical reporting. Wireless device 110 may receive informationindicating the at least one measurement quantity from a network node.

For example, in a particular embodiment, the at least one measurementquantity indicates that only beam indexes are to be reported as part ofbeam level reporting, and wireless device 110 sorts the plurality ofmeasurements based on RSRP.

In another example embodiment, the at least one measurement quantityindicates RSRP, and wireless device 110 sorts the plurality ofmeasurements based on RSRP.

In yet another example embodiment, the at least one measurement quantityindicates RSRQ, and wireless device 110 sorts the plurality ofmeasurements are sorted based on RSRQ.

In still another example embodiment, the at least one measurementquantity indicates SINR, and wireless device 110 sorts the plurality ofmeasurements based on SINR.

In yet another example embodiment, the at least one measurement quantityindicates RSRP and at least one of SINR and RSRQ, and wireless device110 sorts the plurality of measurements based on RSRP.

In a particular embodiment, the wireless device is configured forevent-triggered reporting and the at least one measurement quantitycomprises a trigger quantity.

In a particular embodiment, the plurality of measurements comprises oneor more measurements for a neighbouring cell of the wireless device, andwireless device 110 sorts the one or more measurements for theneighbouring cell to identify at least one best neighbouring cell thatdoes not to exceed a maximum number of cells to be reported. In aparticular embodiment, a best one of the plurality of a measurements ofa measurement type associated with the trigger quantity may be reportedfirst in the measurement report.

FIG. 16 illustrates a schematic block diagram of an apparatus 1300 in awireless network (for example, the wireless network shown in FIG. 2).The apparatus may be implemented in a wireless device or network node(e.g., wireless device 110 or network node 160 shown in FIG. 2).Apparatus 1300 is operable to carry out the example method describedwith reference to FIG. 15 and possibly any other processes or methodsdisclosed herein. It is also to be understood that the method of FIG. 15is not necessarily carried out solely by apparatus 1300. At least someoperations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to cause sortingunit 1310, reporting unit 1320, and any other suitable units ofapparatus 1300 to perform corresponding functions according one or moreembodiments of the present disclosure, such as the functionalitydescribed in FIG. 15.

For example, sorting unit 1310 may perform the sorting functions of theapparatus 1300. In a particular embodiment, sorting unit 1310 may sort aplurality of measurements for a measurement report based on at least onemeasurement quantity.

For example, reporting unit 1320 may perform the reporting functions ofthe apparatus 1300. In a particular embodiment, reporting unit 1320 mayto a network node 160 a measurement report comprising measurementinformation selected from the plurality of measurements based on thesorting of the plurality of measurements based on the at least onemeasurement quantity.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

FIG. 17 depicts a method by a network node 160 for configuring awireless device 110 for measurement reporting, according to certainembodiments. The method begins at step 1410 when network node 160configures wireless device 110 for event-based measurement reporting.

In a particular embodiment, the plurality of measurements comprises beamlevel measurements. Additionally or alternatively, the plurality ofmeasurements comprise cell level measurements.

In a particular embodiment, the plurality of measurements are for aserving cell of wireless device 110. Additionally or alternatively, in aparticular embodiment, the plurality of measurements are for aneighbouring cell of wireless device 110.

At step 1420, network node 160 receives, from wireless device 110, ameasurement report comprising measurement information selected from aplurality of measurements based on a sorting of the plurality ofmeasurements. The sorting of the plurality of measurements is inresponse to detection of an event.

In a particular embodiment, the measurement information includes atleast one of the plurality of measurements. Additionally oralternatively, in a particular embodiment, the measurement informationincludes beam indexes.

In a particular embodiment, the measurement report may include beamlevel information of a PCell and a SCell.

In a particular embodiment, the plurality of measurements are sorted forthe measurement report based on at least one measurement quantity.

In a particular embodiment, the measurement quantity is a reportquantity configured by the network.

In a particular embodiment, the measurement quantity is a triggerquantity out of a set of multiple trigger quantities configured by thenetwork.

According to certain particular embodiments, network node 160 maytransmit information indicating the at least one measurement quantity tothe wireless device.

In a particular example embodiment, the at least one measurementquantity indicates that only beam indexes are to be reported as part ofbeam level reporting and the plurality of measurements are sorted basedon RSRP.

In another example embodiment, the at least one measurement quantityindicates RSRP and the plurality of measurements are sorted based onRSRP.

In still another example embodiment, the at least one measurementquantity indicates RSRQ and the plurality of measurements are sortedbased on RSRQ.

In yet another example embodiment, the at least one measurement quantityindicates SINR and the plurality of measurements are sorted based onSINR.

In yet another example embodiment, the at least one measurement quantityindicates RSRP and at least one of SINR and RSRQ, and the plurality ofmeasurements is sorted based on RSRP.

In a particular embodiment, configuring the wireless device 110 forevent-based measurement reporting may include configuring the wirelessdevice 110 for event-triggered reporting and the at least onemeasurement quantity includes a trigger quantity.

In a particular embodiment, a best one of the plurality of ameasurements of a measurement type associated with the trigger quantityis reported first in the measurement report.

In a particular embodiment, network node 160 may configure wirelessdevice 110 for periodical reporting.

In a particular embodiment, the plurality of measurements include one ormore measurements for a neighbouring cell of the wireless device and theone or more measurements for the neighbouring cell are sorted toidentify at least one best neighbouring cell. The at least one bestneighbouring cell does not to exceed a maximum number of cells to bereported.

FIG. 18 illustrates a schematic block diagram of an apparatus 1500 in awireless network (for example, the wireless network shown in FIG. 2).The apparatus may be implemented in a wireless device or network node(e.g., wireless device 110 or network node 160 shown in FIG. 2).Apparatus 1500 is operable to carry out the example method describedwith reference to FIG. 17 and possibly any other processes or methodsdisclosed herein. It is also to be understood that the method of FIG. 17is not necessarily carried out solely by apparatus 1500. At least someoperations of the method can be performed by one or more other entities.

Virtual Apparatus 1500 may comprise processing circuitry, which mayinclude one or more microprocessor or microcontrollers, as well as otherdigital hardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory, cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to causeconfiguring unit 1510, receiving unit 1520, and any other suitable unitsof apparatus 1500 to perform corresponding functions according one ormore embodiments of the present disclosure, such as the functionalitydescribed in FIG. 17.

For example, configuring unit 1510 may perform the configuring functionsof the apparatus 1500. In a particular embodiment, configuring unit 1510may configure wireless device 110 for event-based measurement reporting.

For example, receiving unit 1520 may perform the receiving functions ofthe apparatus 1500. In a particular embodiment, receiving unit 1520 mayreceive, from wireless device 110, a measurement report comprisingmeasurement information selected from a plurality of measurements basedon a sorting of the plurality of measurements in response to detectionof an event.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, memories, logic solid state and/or discrete devices,computer programs or instructions for carrying out respective tasks,procedures, computations, outputs, and/or displaying functions, and soon, as such as those that are described herein.

Example Embodiments

According to certain example embodiments, a method performed by awireless device for measurement reporting comprises: determining whetherevent triggered, periodical, and/or beam reporting is configured for thewireless device; sorting neighbour cell measurement results for ameasurement report based on the determinations; and reporting to anetwork node a measurement report based on the determinations andsorting. Optionally, the method may further include providing user dataand forwarding the user data to a host computer via the transmission tothe base station.

According to certain example embodiments, a wireless device formeasurement reporting includes processing circuitry configured toperform any of the steps of the example embodiments above and powersupply circuitry configured to supply power to the wireless device.

According to certain example embodiments, a UE for measurement reportingincludes: an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processingcircuitry and configured to condition signals communicated between theantenna and the processing circuitry; the processing circuitry beingconfigured to perform any of the steps of the example embodiments above;an input interface connected to the processing circuitry and configuredto allow input of information into the UE to be processed by theprocessing circuitry; an output interface connected to the processingcircuitry and configured to output information from the UE that has beenprocessed by the processing circuitry; and a battery connected to theprocessing circuitry and configured to supply power to the UE.

According to certain example embodiments, a communication systemincluding a host computer comprises processing circuitry configured toprovide user data and a communication interface configured to forwarduser data to a cellular network for transmission to a user equipment(UE), wherein the UE comprises a radio interface and processingcircuitry, the UE's components configured to perform any of the steps ofany of the example embodiments above. Optionally, the cellular networkfurther includes a base station configured to communicate with the UE.Optionally, the communication system of the previous 2 embodiments,wherein the processing circuitry of the host computer is configured toexecute a host application, thereby providing the user data and the UE'sprocessing circuitry is configured to execute a client applicationassociated with the host application.

According to certain example embodiments, a method implemented in acommunication system including a host computer, a base station and auser equipment (UE) comprises: at the host computer, providing userdata; and at the host computer, initiating a transmission carrying theuser data to the UE via a cellular network comprising the base station,wherein the UE performs any of the steps of any of the exampleembodiments above. Optionally, the method of the previous embodiment,further comprises at the UE, receiving the user data from the basestation.

According to certain example embodiments, a communication systemincluding a host computer comprises: communication interface configuredto receive user data originating from a transmission from a UE to a basestation, wherein the UE comprises a radio interface and processingcircuitry, the UE's processing circuitry configured to perform any ofthe steps of any of the example embodiments above. Optionally, thecommunication system of the previous embodiment further includes the UE.Optionally, the communication system of the previous embodiments,further includes the base station, wherein the base station comprises aradio interface configured to communicate with the UE and acommunication interface configured to forward to the host computer theuser data carried by a transmission from the UE to the base station.Optionally, the communication system of the previous embodiments,wherein: the processing circuitry of the host computer is configured toexecute a host application and the UE's processing circuitry isconfigured to execute a client application associated with the hostapplication, thereby providing the user data. Optionally, the processingcircuitry of the host computer is configured to execute a hostapplication, thereby providing request data and the UE's processingcircuitry is configured to execute a client application associated withthe host application, thereby providing the user data in response to therequest data.

According to certain example embodiments, a method implemented in acommunication system includes a host computer, a base station and a userequipment (UE), and the method comprises at the host computer, receivinguser data transmitted to the base station from the UE, wherein the UEperforms any of the steps of any of the example embodiments above.Optionally, the method further comprises, at the UE, providing the userdata to the base station. Optionally, the method further comprises, atthe UE, executing a client application, thereby providing the user datato be transmitted and, at the host computer, executing a hostapplication associated with the client application. Optionally, themethod further includes, at the UE, executing a client application and,at the UE, receiving input data to the client application, the inputdata being provided at the host computer by executing a host applicationassociated with the client application, wherein the user data to betransmitted is provided by the client application in response to theinput data.

According to certain example embodiments, a method implemented in acommunication system that includes a host computer, a base station and auser equipment (UE) includes, at the host computer, receiving, from thebase station, user data originating from a transmission which the basestation has received from the UE, wherein the UE performs any of thesteps of any of example embodiments above. Optionally, the methodfurther comprises, at the base station, receiving the user data from theUE. Optionally, the method further includes, at the base station,initiating a transmission of the received user data to the hostcomputer.

Abbreviations

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   1×RTT CDMA2000 1× Radio Transmission Technology    -   3GPP 3rd Generation Partnership Project    -   5G 5th Generation    -   ABS Almost Blank Subframe    -   ARQ Automatic Repeat Request    -   AWGN Additive White Gaussian Noise    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   CA Carrier Aggregation    -   CC Carrier Component    -   CCCH SDU Common Control Channel SDU    -   CDMA Code Division Multiplexing Access    -   CGI Cell Global Identifier    -   CIR Channel Impulse Response    -   CP Cyclic Prefix    -   CPICH Common Pilot Channel    -   CPICH Ec/No CPICH Received energy per chip divided by the power        density in the band    -   CQI Channel Quality information    -   C-RNTI Cell RNTI    -   CSI Channel State Information    -   DCCH Dedicated Control Channel    -   DL Downlink    -   DM Demodulation    -   DMRS Demodulation Reference Signal    -   DRX Discontinuous Reception    -   DTX Discontinuous Transmission    -   DTCH Dedicated Traffic Channel    -   DUT Device Under Test    -   E-CID Enhanced Cell-ID (positioning method)    -   E-SMLC Evolved-Serving Mobile Location Centre    -   ECGI Evolved CGI    -   eNB E-UTRAN NodeB    -   ePDCCH enhanced Physical Downlink Control Channel    -   E-SMLC evolved Serving Mobile Location Center    -   E-UTRA Evolved UTRA    -   E-UTRAN Evolved UTRAN    -   FDD Frequency Division Duplex    -   FFS For Further Study    -   GERAN GSM EDGE Radio Access Network    -   gNB Base station in NR    -   GNSS Global Navigation Satellite System    -   GSM Global System for Mobile communication    -   HARQ Hybrid Automatic Repeat Request    -   HO Handover    -   HSPA High Speed Packet Access    -   HRPD High Rate Packet Data    -   LOS Line of Sight    -   LPP LTE Positioning Protocol    -   LTE Long-Term Evolution    -   MAC Medium Access Control    -   MBMS Multimedia Broadcast Multicast Services    -   MBSFN Multimedia Broadcast multicast service Single Frequency        Network    -   MBSFN ABS MBSFN Almost Blank Subframe    -   MDT Minimization of Drive Tests    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   NPDCCH Narrowband Physical Downlink Control Channel    -   NR New Radio    -   OCNG OFDMA Channel Noise Generator    -   OFDM Orthogonal Frequency Division Multiplexing    -   OFDMA Orthogonal Frequency Division Multiple Access    -   OSS Operations Support System    -   OTDOA Observed Time Difference of Arrival    -   O&M Operation and Maintenance    -   PBCH Physical Broadcast Channel    -   P-CCPCH Primary Common Control Physical Channel    -   PCell Primary Cell    -   PCFICH Physical Control Format Indicator Channel    -   PDCCH Physical Downlink Control Channel    -   PDP Profile Delay Profile    -   PDSCH Physical Downlink Shared Channel    -   PGW Packet Gateway    -   PHICH Physical Hybrid-ARQ Indicator Channel    -   PLMN Public Land Mobile Network    -   PMI Precoder Matrix Indicator    -   PRACH Physical Random Access Channel    -   PRS Positioning Reference Signal    -   PSS Primary Synchronization Signal    -   PUCCH Physical Uplink Control Channel    -   PUSCH Physical Uplink Shared Channel    -   RACH Random Access Channel    -   QAM Quadrature Amplitude Modulation    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RLM Radio Link Management    -   RNC Radio Network Controller    -   RNTI Radio Network Temporary Identifier    -   RRC Radio Resource Control    -   RRM Radio Resource Management    -   RS Reference Signal    -   RSCP Received Signal Code Power    -   RSRP Reference Symbol Received Power OR Reference Signal        Received Power    -   RSRQ Reference Signal Received Quality OR Reference Symbol        Received Quality    -   RSSI Received Signal Strength Indicator    -   RSTD Reference Signal Time Difference    -   SCH Synchronization Channel    -   SCell Secondary Cell    -   SDU Service Data Unit    -   SFN System Frame Number    -   SGW Serving Gateway    -   SI System Information    -   SIB System Information Block    -   SNR Signal to Noise Ratio    -   SON Self Optimized Network    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   TDD Time Division Duplex    -   TDOA Time Difference of Arrival    -   TOA Time of Arrival    -   TSS Tertiary Synchronization Signal    -   TTI Transmission Time Interval    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunication System    -   USIM Universal Subscriber Identity Module    -   UTDOA Uplink Time Difference of Arrival    -   UTRA Universal Terrestrial Radio Access    -   UTRAN Universal Terrestrial Radio Access Network    -   WCDMA Wide CDMA    -   WLAN Wide Local Area Network

1. A method performed by a wireless device for measurement reporting,the method comprising: receiving a reporting configuration from anetwork node, the reporting configuration specifying a plurality ofdifferent report quantities to be included in a measurement report;determining whether to use Reference Signal Received Power (RSRP) orReference Signal Received Quality (RSRQ) as a measurement quantity forsorting of beam-level measurements based on the plurality of reportingquantities specified in the reporting configuration; sorting a pluralityof beam-level measurements for a periodical measurement report based onat least the determined measurement quantity; and reporting to a networknode the measurement report comprising measurement information selectedfrom the plurality of beam-level measurements based on the sorting ofthe plurality of beam-level measurements based on at least thedetermined measurement quantity.
 2. The method of claim 1, wherein themeasurement quantity is a report quantity configured by the network. 3.The method of claim 1, wherein the plurality of beam-level measurementsare for a serving cell of the wireless device.
 4. The method of claim 1,wherein the plurality of beam-level measurements are for a neighbouringcell of the wireless device.
 5. The method of claim 1, wherein:determining that RSRP is to be used as the measurement quantity when thereporting configuration received from the network node indicates thatonly beam indexes are to be reported as part of beam level reporting;and sorting the plurality of beam-level measurements comprises sortingthe plurality of beam-level measurements based on RSRP.
 6. The method ofclaim 1, wherein: determining that RSRP is to be used as the measurementquantity when the reporting configuration received from the network nodeindicates RSRP as one of the plurality of different report quantities;and sorting the plurality of beam-level measurements comprises sortingthe plurality of beam-level measurements based on RSRP.
 7. The method ofclaim 1, wherein: determining that RSRQ is to be used as the measurementquantity when the reporting configuration received from the network nodedoes not indicate RSRP as one of the plurality of different reportquantities; and sorting the plurality of beam-level measurementscomprises sorting the plurality of beam-level measurements based onRSRQ.
 8. A wireless device for measurement reporting, the wirelessdevice comprising: processing circuitry configured to: receive areporting configuration from a network node, the reporting configurationspecifying a plurality of different report quantities to be included ina measurement report; determine whether to use Reference Signal ReceivedPower (RSRP) or Reference Signal Received Quality (RSRQ) as ameasurement quantity for sorting of beam-level measurements based on theplurality of reporting quantities specified in the reportingconfiguration; sort a plurality of beam-level measurements for aperiodical measurement report based on at least the determinedmeasurement quantity; and report to a network node the measurementreport comprising measurement information selected from the plurality ofbeam-level measurements based on the sorting of the plurality ofbeam-level measurements based on at least the determined measurementquantity.
 9. The wireless device of claim 8, wherein the measurementquantity is a report quantity configured by the network.
 10. Thewireless device of claim 8, wherein the plurality of beam-levelmeasurements are for a serving cell of the wireless device.
 11. Thewireless device of claim 8, wherein the plurality of beam-levelmeasurements are for a neighbouring cell of the wireless device.
 12. Thewireless device of claim 8, wherein the processing circuitry is furtherconfigured to: determine that RSRP is to be used as the measurementquantity when the reporting configuration received from the network nodeindicates that only beam indexes are to be reported as part of beamlevel reporting; and sort the plurality of beam-level measurements basedon RSRP.
 13. The wireless device of claim 8, wherein the processingcircuitry is further configured to: determine that RSRP is to be used asthe measurement quantity when the reporting configuration received fromthe network node indicates RSRP as one of the plurality of differentreport quantities; and sort the plurality of beam-level measurementsbased on RSRP.
 14. The wireless device of claim 8, wherein theprocessing circuitry is further configured to: determine that RSRQ is tobe used as the measurement quantity when the reporting configurationreceived from the network node does not indicate RSRP as one of theplurality of different report quantities; and sort the plurality ofbeam-level measurements based on RSRQ.
 15. A method performed by anetwork node for configuring a wireless device for measurementreporting, the method comprising: sending the wireless device areporting configuration specifying a plurality of different reportquantities to be included in a measurement report, the plurality ofdifferent report quantities for use in determining whether to useReference Signal Received Power (RSRP) or Reference Signal ReceivedQuality (RSRQ) as a measurement quantity for sorting of beam-levelmeasurements; configuring the wireless device periodical measurementreporting; and receiving, from the wireless device, a measurement reportcomprising measurement information selected from a plurality ofbeam-level measurements based on a sorting of the plurality ofbeam-level measurements, the sorting of the plurality of beam-levelmeasurements performed based on the determined measurement quantity. 16.The method of claim 15, wherein the plurality of beam-level measurementsare for a serving cell of the wireless device.
 17. The method of claim15, wherein the plurality of beam-level measurements are for aneighbouring cell of the wireless device.
 18. The method of claim 15,wherein: the wireless device determines that RSRP is to be used as themeasurement quantity when the reporting configuration indicates thatonly beam indexes are to be reported as part of beam level reporting;and the plurality of beam-level measurements are sorted based on RSRP.19. The method of claim 15, wherein: the wireless device determines thatRSRP is to be used as the measurement quantity when the reportingconfiguration indicates RSRP as one of the plurality of different reportquantities; and the plurality of beam-level measurements are sortedbased on RSRP.
 20. The method of claim 15, wherein: the wireless devicedetermines that RSRQ is to be used as the measurement quantity when thereporting configuration does not indicate RSRP as one of the pluralityof different report quantities; and the plurality of beam-levelmeasurements are sorted based on RSRQ.
 21. A network node forconfiguring a wireless device for measurement reporting, the networknode comprising: processing circuitry configured to: send the wirelessdevice a reporting configuration specifying a plurality of differentreport quantities to be included in a measurement report, the pluralityof different report quantities for use in determining whether to useReference Signal Received Power (RSRP) or Reference Signal ReceivedQuality (RSRQ) as a measurement quantity for sorting of beam-levelmeasurements; configure the wireless device periodical measurementreporting; and receive, from the wireless device, a measurement reportcomprising measurement information selected from a plurality ofbeam-level measurements based on a sorting of the plurality ofbeam-level measurements, the sorting of the plurality of beam-levelmeasurements performed based on the determined measurement quantity. 22.The network node of claim 21, wherein the plurality of beam-levelmeasurements are for a serving cell of the wireless device.
 23. Thenetwork node of claim 21, wherein the plurality of beam-levelmeasurements are for a neighbouring cell of the wireless device.
 24. Thenetwork node of claim 21, wherein: the wireless device determines thatRSRP is to be used as the measurement quantity when the reportingconfiguration indicates that only beam indexes are to be reported aspart of beam level reporting; and the plurality of beam-levelmeasurements are sorted based on RSRP.
 25. The network node of claim 21,wherein: the wireless device determines that RSRP is to be used as themeasurement quantity when the reporting configuration indicates RSRP asone of the plurality of different report quantities; and the pluralityof beam-level measurements are sorted based on RSRP.
 26. The networknode of claim 21, wherein: the wireless device determines that RSRQ isto be used as the measurement quantity when the reporting configurationdoes not indicate RSRP as one of the plurality of different reportquantities; and the plurality of beam-level measurements are sortedbased on RSRQ.